Workout monitor interface

ABSTRACT

The present disclosure relates to systems and processes for monitoring a workout and for generating improved interfaces for the same. An electronic device displays a first user interface in response to initiating a workout session. In addition, the electronic device receives an input while displaying the first user interface, and in response to the input, ceases to display the first user interface and displays a second user interface associated with a music application of the electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/600,243, entitled “WORKOUT MONITOR INTERFACE,” filed on May 19, 2017,which claims priority to U.S. Provisional Patent Application Ser. No.62/398,440, entitled “WORKOUT MONITOR INTERFACE,” filed on Sep. 22,2016. The contents of each of which are hereby incorporated by referencein their entirety.

FIELD

The following disclosure relates generally to a computer user interfacesand, more specifically, to techniques and devices for presenting workoutmonitor interfaces.

BACKGROUND

Whether an individual is exercises for health or competition, theeffectiveness of exercise can be improved with real-time feedback ofperformance and physiological attributes associated with the exercise.For example, data about an individual's heartrate can help theindividual determine whether they are in the target heartrate zone for adesired level of activity or whether the individual is over or underexerting themselves. Additionally, performance during exercise can helpmotivate and track and individual's progress, which aids in reachinggoals or even just maintaining a healthy level of exercise.

SUMMARY

Some techniques for presenting workout monitor interfaces usingelectronic devices, however, are generally cumbersome and inefficient.For example, some existing techniques use a complex and time-consuminguser interface, which may include multiple key presses, keystrokes, orother user inputs. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for workout monitoring.Such methods and interfaces optionally complement or replace othermethods for workout monitoring. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated computing devices, such methods andinterfaces conserve power and increase the time between battery charges.

The present disclosure relates to systems and processes for monitoring aworkout and for generating improved interfaces for the same. One exampleuser interface detects when a workout of a particular type is startedand begins generating activity data related to workout metricsassociated with the type of workout selected. Using determined currentvalues for the workout metrics, the example user interface displays apro-view (“professional” view) display that includes indicators for theworkout metrics associated with the selected workout type. The pro-viewdisplay also includes a focus indicator that highlights a selectedindicator representative of a focused workout metric. The focusindicator is movable among the indicators representative of the workoutmetrics based on user input. Upon detection of a gesture, the exampleuser interface transitions to a simple-view display that includes anindicator representative of the focused workout metric. The simple-viewdisplay includes indicators for less than all of the workout metricsassociated with the selected workout type. The example user interfacereceives input to change the focused workout metric in the simple-viewdisplay. The example user interface also receives a gesture totransition the simple-view display back to the pro-view display.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for workout monitoring, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace other methods for monitoringworkouts.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some examples.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some examples

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some examples

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with some examples.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someexamples.

FIG. 5A illustrates a portable multifunction device having atouch-sensitive display in accordance with some examples.

FIG. 5B is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some examples.

FIG. 6 illustrates a block diagram of an exemplary system foraggregating wellness data according to various examples.

FIG. 7 illustrates a block diagram of another exemplary system foraggregating wellness data according to various examples.

FIG. 8 illustrates an exemplary physical interface for displaying a menuof applications according to various examples.

FIG. 9 illustrates a process for generating a workout interface formonitoring a user's workout according to various examples.

FIGS. 10-12 illustrate exemplary interfaces of a physical activityapplication according to various examples.

FIGS. 13, 14, 17, 18, and 21 illustrate exemplary interfaces of apro-view display according to various examples.

FIGS. 15, 16, 19, 20 illustrate exemplary interfaces of a simple-viewdisplay according to various examples.

FIGS. 22-23 illustrate exemplary workout controls according to variousexamples.

FIG. 24 illustrates exemplary music controls according to variousexamples.

FIG. 25 illustrates functional block diagrams of electronic devicesaccording to various examples.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for workout monitoring. Such techniques can reduce thecognitive burden on a user who accesses workout information, therebyenhancing productivity. Further, such techniques can reduce processorand battery power otherwise wasted on redundant user inputs.

FIGS. 1A-1B, 2, 3, and 5A-B illustrate exemplary devices for monitoringa user's workout. FIGS. 6 and 7 illustrate exemplary systems formonitoring a user's workout. FIGS. 8, 13-24 illustrate exemplary userinterfaces associated with monitoring a user's workout. FIG. 9 is a flowdiagram illustrating methods of monitoring a user's workout inaccordance with some embodiments. The user interfaces in FIGS. 8, 13-24are used to illustrate the processes described below, including theprocess in FIG. 9. FIG. 25 shows an exemplary functional block diagramof an electronic device 800 configured in accordance with the principlesof the various described embodiments.

Exemplary Devices

Although the following description uses terms first, second, etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for monitoring aworkout. FIGS. 10-24 illustrate exemplary user interfaces for monitoringa workout. FIG. 9 is a flow diagram illustrating methods of managingevent notifications in accordance with some embodiments. The userinterfaces in FIGS. 10-24 are used to illustrate the processes describedbelow, including the processes in FIG. 9.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes one or more computer-readable storagemediums. The computer-readable storage mediums are optionallynon-transitory. The computer-readable storage mediums are optionallytransitory. Memory 102 optionally includes high-speed random accessmemory and optionally also includes non-volatile memory, such as one ormore magnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. Nos. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described below, including process 900 (FIG. 9). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A-B, 3, and5A-B). For example, an image (e.g., icon), a button, and text (e.g.,hyperlink) each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

Exemplary User Interfaces

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIG. 6 illustrates an example system 600 for aggregating wellness andother types of data. Wellness data can include, but is not limited to,any type of data associated with a person's health, such as theirphysical activity data, workout data, weight, heart rate, bloodpressure, blood glucose level, medication compliance, or the like.System 600 can be used to collect wellness data associated with a user,store the wellness data, present the wellness data to the user in usefulways, and selectively share the user's wellness data with other users orentities based on permissions set by the user. In addition, in someexamples, system 600 can further be used to collect non-wellness dataalong with wellness data, correlate the non-wellness data with thewellness data, and display the non-wellness data with the wellness data.

System 600 can include one or more user devices 610, which can includeany type of electronic device, such as a mobile phone, tablet computer,desktop computer, laptop computer, PDA, or the like. In some examples,user device 610 can include a device similar or identical to devices100, 300, or 500, described above. User device 610 can include anoperating system and a wellness database 611 (e.g., memory 102, 370, or518) for securely storing wellness or non-wellness data along withassociated metadata, such as the time the data was recorded, type ofdata, device used to record the data, user associated with the data, andthe like. User device 610 can further include application programminginterfaces (APIs) with access controls for storing data in the wellnessdatabase 611 and for accessing data stored in the wellness database 611.

User device 610 can be configured to receive wellness or non-wellnessdata from various sources and can store the received data in thewellness database 611. For example, user device 610 can be configured toreceive wellness or non-wellness data from sensors 602, 604, 606, and608. These sensors can include any type of sensor capable of obtainingwellness data, such as a biometric sensor, activity tracker, or thelike. For example, sensors 602, 604, 606, and 608 can include, but arenot limited to, a scale, blood pressure cuff, blood glucose monitor,electrocardiogram, step counter, gyroscope, accelerometer, SpO2 sensor,respiration sensor, posture sensor, stress sensor, photoplethysmogram,galvanic skin response sensor, temperature sensor, or the like. Sensors602, 604, 606, and 608 can also include other types of sensors, such asaudio sensors, ambient light sensors, electromagnetic sensors, touchsensors, capacitive sensors, and the like, for obtaining non-wellnessdata, such as situational data, temporal data, personal data, contactdata, and the like data. In some examples, each sensor can be a separatedevice, while, in other examples, any combination of two or more of thesensors can be included within a single device. For example, thegyroscope, accelerometer, photoplethysmogram, galvanic skin responsesensor, and temperature sensor can be included within a wearableelectronic device, such as a smart watch, while the scale, bloodpressure cuff, blood glucose monitor, Sp02 sensor, respiration sensor,posture sensor, stress sensor, and asthma inhaler can each be separatedevices. While specific examples are provided, it should be appreciatedthat other sensors can be used and other combinations of sensors can becombined into a single device.

Sensors 602, 604, 606, and 608 can be used to measure wellness ornon-wellness data continuously, intermittently, periodically, or at anyother desired frequency or interval of time. For example, sensors 602,604, 606, and 608 can be used to obtain a single measurement or multiplemeasurements over a length of time. Sensors 602, 604, 606, and 608 canbe configured to measure wellness or non-wellness data at the sameintervals of time, or can be configured to measure wellness ornon-wellness data at different intervals of time. These intervals may beset by a user or may be a default setting for each sensor. Additionally,sensors 602, 604, 606, 608 can be used to measure wellness ornon-wellness data at any time or location desired by the user. Moreover,sensors 602, 604, 606, and 608 can be used with or without thesupervision of a healthcare provider. For example, a user can usesensors 602, 604, 606, and 608 to obtain sensor measurements at homewithout the supervision of a medical professional.

In some examples, user device 610 can include software sensorapplications 613 (e.g., third party applications) associated with eachof sensors 602, 604, 606, and 608 for interfacing with the sensors toallow user device 610 to receive the wellness or non-wellness data. Inthese examples, the applications 613 can use the device's APIs to storethe wellness or non-wellness data in the wellness database 611 of userdevice 610. In some examples, device 610 can be a smart phone, tabletcomputer, or the like, and the software sensor applications 613 caninclude software applications downloadable onto device 610. It should beunderstood that “third party” can correspond to an entity different thanthe manufacturer of device 610 and/or the entity that created and/ormaintains the operating system of device 610. In these instances, thirdparty applications and their corresponding sensors can communicate andfunction within the operating system of device 610 according to apredefined device protocol associated with device 610.

The applications 613 can similarly use the device's APIs to access datastored in the wellness database 611. In other examples, user device 610can be configured to share one or more communication formats withsensors 602, 604, 606, and 608 to allow user device 610 to receive andinterpret the wellness or non-wellness data from the sensors. Thereceived data can then be stored in the wellness database 611 of userdevice 610.

User device 610 can further receive wellness or non-wellness data fromits own wellness or non-wellness data sensors 620 (e.g., sensors 168,359, and 520), from a user interacting with user device 610, fromanother entity, such as a physician, or from other non-sensor sources.For example, using the device's APIs, wellness or non-wellness data canbe received from applications 617 (third party or first partyapplications) on user device 610, such as a clock application, acalendaring application, a gaming application, an application from ahealthcare provider, a messaging application, a physical activityapplication, a workout application, or the like. The wellness ornon-wellness data from the applications 617 can originate from sensors620, a user interacting with the applications, a remote database (e.g.,database for a medical website), a healthcare provider institution(e.g., via the institution's application 617), or the like. In theseexamples, the usage of the application 617 (e.g., how long you play avideo game application, when you play the video game, number of timesinteracting with a stock application, number of times interacting with asocial networking application, length of time interacting with a socialnetworking application, etc.), usage of user device 610 (e.g., length oftime on the phone or number of text messages sent as determined from aphone payment application, time spent browsing the Internet asdetermined from the device's browser, etc.), time spent listening tomusic as determined from a music or streaming radio application, timespent using a remote application for controlling a television, amount oftime or money spent on shopping websites, weather data from a weatherapplication (e.g., to determine how weather affects a user's health),type of events occurring in the user's life as determined from acalendar (e.g., meetings, birthdays, holidays, etc.), interactions withcertain people as determined from a contact list and/or calendarapplication and/or a messaging application and/or phone of user device610, or the like, can be received by user device 610 and stored in thewellness database 611.

In some examples, default or user-selected settings can be provided torestrict the access that at least one application (e.g., at least one ofapplications 613 and 617) on user device 610 has to the wellnessdatabase 611 of user device 610 (for both storage and retrievalpurposes) and to the sensor data generated by sensors 620 within userdevice 610 and/or sensor data generated by sensors 602, 604, 606, and608. For example, an application for tracking a user's running sessionscan be granted access to the data generated by the GPS sensor of userdevice 610, but can be prevented from accessing the user's bloodpressure data stored in the wellness database 611. In some examples, anentity other than the owner of user device 610 can set the authorizationsettings for various applications on user device 610. For example, themanufacturer of user device 610 and/or the entity that created and/ormaintains the operating system of user device 610 can evaluate theapplications to determine if they should be given access to the user'swellness data and/or sensor data generated or received by user device610. In some examples, these settings can be overridden by the user.User device 610 can further include a display for displaying the storedwellness data or non-wellness data.

FIG. 7 illustrates system 700 for sharing user wellness data. System 700can include user server 714 communicatively coupled to user device 610via network 712, which can include the Internet, an intranet, or anyother wired or wireless public or private network. User device 610 canbe configured to securely transmit the aggregated wellness ornon-wellness data and associated metadata stored on the device to userserver 714 for storage in user database 716. In some examples, thewellness or non-wellness data and associated metadata can be transmittedto user server 714 for storage in user database 716 in response to anexplicit request for such a transfer by the user of device 610, while,in other examples, the wellness or non-wellness data can be synced withthe data in user database 716 continuously, periodically,intermittently, or at any desired frequency. In yet other examples, theuser's wellness or non-wellness data can be stored only on user device610 and may not be stored in an external database.

In some examples, user server 714 and user database 716 can beconfigured to securely store a user's wellness or non-wellness datausing a public/private key system that only allows the owner of thewellness or non-wellness data to decrypt the data. Additionally, thewellness or non-wellness data stored in user database 716 can be storedanonymously (e.g., without identifying and/or personal information aboutthe user, such as a legal name, username, time and location data, or thelike). In this way, other users, hackers, and the owner/operator of userdatabase 716 cannot determine the identity of the user associated withthe data stored in database 716. In some examples, a user can accesstheir wellness or non-wellness data stored in user database 716 from auser device that is different than the one used to upload the wellnessor non-wellness data to user server 714. In these instances, the usercan be required to provide login credentials to access their wellness ornon-wellness data. User server 714 can be configured to perform theauthorization process to restrict access to the data within userdatabase 716.

System 700 can further include any number of other user devices 722 and724 coupled to network 712. In some examples, user devices 722 and 724can be operated by the same user as user device 610. In these instances,the user can access their wellness or non-wellness data stored in userdatabase 716 by providing user server 714 with the appropriatecredentials. In some examples, wellness and non-wellness data can besynced between user database 716 and one or more of user device 610,722, and 724. In other examples, the user of user devices 722 and 724can be a person that is different than the user of user device 610. Inthese examples, the users of devices 722 and 724 cannot access thewellness or non-wellness data of the user of user device 610 without theauthorization of the user of user device 610. If authorization is given,wellness or non-wellness data can be shared with the users of userdevices 722 and 724.

In some examples, any of the above described sources of wellness ornon-wellness data can be configured to measure, generate, or receivewellness or non-wellness data continuously, intermittently,periodically, or at any other desired frequency or interval of time. Assuch, the wellness or non-wellness data can similarly be stored orupdated in wellness database 611 or user database 716 continuously,intermittently, periodically, or at any other desired frequency orinterval of time. The frequencies and intervals of time used formeasuring, generating, receiving, or storing wellness or non-wellnesscan be the same or they can be different. Additionally, thesefrequencies and intervals can be default values or they can be set by auser to provide the user with wellness or non-wellness data that hasbeen updated within a desired length of time.

While not shown, it should be appreciated that many other user devicescan be coupled to user server 714 through network 712 to collect andstore wellness or non-wellness data for other users in a manner similarto that described above.

Workout Monitor

FIG. 8 illustrates an exemplary interface 800 for displaying a menu ofapplications on an electronic device, such as device 100, 300, 500, or610. As shown, interface 800 includes multiple application icons 802that, when selected by a user, causes the electronic device to open theassociated application. For example, in response to a user selection ofan application icon 802 corresponding to a workout application formonitoring a user's workout, the workout application can be opened andprocess 900, shown in FIG. 9, can be performed. Process 900 can beperformed by device 100, 300, 500, or 610 to detect movement associatedwith the device during a workout, recognizing it as being associatedwith a physical activity performed by the user using the device,monitoring various metrics of the detected physical activity,determining metrics of the workout based on the monitored metrics of thedetected physical activity, and displaying one or more of the metrics ofthe workout on a display of the device.

At block 902, one or more processors of the device can receive aselection of a type of workout. The selected type of workout can includeany type of workout, such as running, walking, cycling, swimming, yoga,dancing, climbing, cross-training, rowing, or the like. In someexamples, the one or more processors of the device can cause, on thedisplay of the device, a display of a list of available types ofworkouts that a user can select. In these examples, the selection of thetype of workout can be received by the one or more processors of thedevice in response to a user indicating a selection of one of thedisplayed available types of workouts (e.g., via mouse click, touch on atouch sensitive display, or the like).

For example, FIG. 10 illustrates an example interface 1000 that can bedisplayed at block 902 of process 900. As shown, interface 1000 caninclude an application identifier 1002 indicating that the “Workout”application is being displayed, a time indicator 1004 indicating thecurrent time, and a list of workout types 1006 that includes a list ofselectable objects associated with available workouts that can beselected by a user. The types of workouts contained in the list ofworkout types 1006 can be ordered in any desired manner, such asalphabetically, by frequency of performance, by time since lastperformed, in a user-selected order, or combinations thereof. Forexample, the first selectable object can correspond to the workout thatwas most recently performed by the user (“Running”), and the remainingselectable objects can be ordered based on a frequency that thecorresponding workouts have been performed. In some examples, the listof workout types 1006 can include more types of workouts than can bedisplayed at one time on the display of the device. In these examples,the device can display the other types of workouts in response to a userinitiating a scroll operation (e.g., by making a swipe or touch and dragmotion on the touch sensitive display). While FIG. 10 shows an examplelist of workout types 1006, it should be appreciated that the list ofworkout types 1006 can include any number and types of workouts.

The type of workout selected in block 902 may have multiple workoutmetrics associated with it. For example, if the workout type “Running”is selected, the workout metrics of elapsed time, distance, pace, andheart rate may be associated with the workout type. In another example,the “Running” workout type may be associated with the elapsed time,distance, pace, heart rate, and calories burned workout metrics. Inanother example, the cycling workout type may be associated with theelapsed time and distance workout metrics. While a few examples ofworkout metrics have been given, other workout metrics may also bepossible, such as speed, rotations per minute (RPM), and laps.

Additionally, while there may be a default set of workout metricsassociated with a given workout type, the set of workout metricsassociated with a workout type may be user configurable via a userconfiguration interface. For example, using a touch-screen or other userinput, a user can select workout metrics that are an associated with agiven workout metric.

FIG. 11 illustrates another example interface 1100 that can be displayedat block 902 of process 900. Similar to interface 1000, interface 1100can include an application identifier 1002, a time indicator 1004, and alist of workout types 1006. However, in interface 1100, one selectableobject associated with a type of workout in the list of workout types1006 can be larger than the selectable objects associated with othertypes of workouts and can include additional information about theworkout type. This selectable object can correspond to the workout thatwas most recently performed by the user. For example, as shown in FIG.11, the selectable object for the “Running” workout type can be twice aslarge as the other selectable objects and can include informationassociated with the most recent workout of that type. In particular,information about the date, distance, pace, and elapsed time of the mostrecent run is displayed on the selectable object for the “Running” typeof workout. The selectable objects below the larger selectable objectcan be ordered based on a frequency that the corresponding workouts areperformed. Alternatively, the objects may be ordered by recency, or acombination of recency and frequency. In some examples, an interfacesimilar to interface 1000 can be displayed the first time that a user isusing the workout application on the device, while an interface similarto interface 1100 can be displayed during any subsequent use of theapplication.

Optionally, in block 902, a later block of process 900, or in a blockafter block 902 that is not depicted in FIG. 9, a goal for the type ofworkout selected can be received. The goal can include an identificationof a workout metric of the selected workout (e.g., a distance, aduration, a number of Calories burned, a pace, or the like) and a goalvalue for the workout metric. For example, for a running type ofworkout, the goal received at block 904 can include a distance workoutmetric and a value of 10 kilometers. Another example goal can include aduration workout metric and a value of 45 minutes, or a Calorie workoutmetric and a value of 110 Calories. In some examples, the one or moreprocessors of the device can cause, on the display of the device, adisplay of an interface that allows the user to select a workout metricof the workout and to enter a desired value for that workout metric.

For example, FIG. 12 illustrates an example interface 1200 that can bedisplayed at block 904 of process 900 in response to receiving aselection of a “running” type of workout at block 902 (e.g., by a userselecting the “Running” option in either interface 1000 or 1100). Asshown, interface 1200 can include a workout type identifier 1202indicating that the “Running” type of workout was selected, a timeindicator 1204 indicating the current time, a value 1206 for the workoutmetric of the workout, buttons 1208 and 1210 for adjusting the value1206, a best value 1212 of the workout metric of the workout, and astart button 1214 for selecting the goal and beginning the workout. Inthis example, the distance workout metric of the workout is beingselected and the value for that workout metric can be selected byadjusting value 1206 up or down using buttons 1210 or 1208,respectively. In other examples, the value for that attribute can beselected by moving (e.g., rotating) a rotatable input mechanism of thedevice. The initial value 1206 displayed in interface 1200 can be adefault value (e.g., 0), a value used in a previous workout, an averagevalue from two or more previous workouts, or any other desired value.Once the desired value 1206 is displayed, a user can select the startbutton 1214 to set the workout goal to be a distance goal having thevalue of value 1206. In some examples, best value 1212 can be selectableand can cause the goal of the workout to be the attribute and value ofthe displayed best value 1212. For example, in response to a selectionof best value 1212 made by a user tapping on the touch-sensitive displayat a location corresponding to best value 1212, the goal of the workoutcan be set to a distance goal of 5.0 miles. In other examples, bestvalue 1212 can represent a value determined based on past performance ofthe user, the user's contacts, the user's friends, a predefined group ofusers, or the like. For example, best value 1212 can instead representthe longest distance run by the user over a predetermined length of time(e.g., the last week), an average distance run by the user, an averagedistance run by the user over a predetermined length of time (e.g., thelast week), a longest distance run by the user'scontacts/friends/running group, a longest distance run by the user'scontacts/friends/running group over a predetermined length of time(e.g., the last week), an average distance run by the user'scontacts/friends/running group, an average distance run by the user'scontacts/friends/running group over a predetermined length of time(e.g., the last week), or the like. In some examples, the device canallow a user to select a different workout metric of the workout as thegoal by displaying a different interface associated with a differentworkout metric of the workout in response to a request from the user. Insome examples, the request can be made by a vertical or horizontal swipegesture across the touch sensitive display of the device, a buttonpress, a movement of a rotatable input mechanism of the device, a usercontact having a characteristic intensity above an intensity thresholdon a display of the device, or any other desired form of input.

In other examples, the device can select from other of interfacessimilar to interface 1200 that allows for other types of goals to beset. For example, while example interfaces for selecting specificworkout metrics for the “Running” type of workout have been provided inFIG. 12, it should be appreciated that interfaces for selecting anyworkout metric of any type of workout can be provided based on the typesof workout metrics associated with the workout type selected at block902. For example, if the type of workout selected at block 902 was“yoga,” an interface for selecting a duration goal or a Calorie goal maybe displayed, but an interface for selecting a distance goal may not bedisplayed.

In some examples, in response to a selection of start button 1214 ininterface 1200, the device can optionally display a countdown beforebeginning the workout selected at block 902 using the selected goal.

Referring back to FIG. 9, at block 904, in response to a request todisplay workout metric data, a pro-view display of the workout metricsassociated with the workout type selected in block 902 is made on thedevice. The request to display workout metric data may take the form of,for example, detection of activity associated with start button 1214 ofFIG. 12. As another example, the request to display workout metric datacould also take the form of the selection of workout type in block 902.As another example, the request to display workout metric data could beassociated with detecting movement or some other information associatedwith sensors 620 of user device 610 (FIG. 6).

The pro-view display includes an indicator representative of each of theplurality of workout metrics associated with the workout type selectedin block 902. For example, FIG. 13 depicts interface 1300, which is anexample of the pro-view displayed in block 904. FIG. 13 is the pro-viewfor the workout type “Running” and includes two associated workoutmetrics. Interface 1300 includes a first indicator 1310 representing afirst workout metric, in this case a distance traveled metric, and asecond indicator 1312 representing a second workout metric, in this casea pace workout metric. Interface 1300 may also include the selectedworkout type in the form of workout type 1302 and other information,such as time 1304.

Interface 1300 also includes a focus indicator 1320 that highlights aworkout metric indicator that is currently selected as the focusedworkout metric. In interface 1300, first indicator 1310 represents thefocused workout metric. The focus indicator 1320 may be a box or othershape around one of the workout metric indicators, but other methods ofhighlighting a workout metric indicator may also be used, such as adifferent coloring, a larger font size, a different background color, orblinking of the indicator. The focus indicator 1320 may be moved toother workout metrics indicators based on, for example, user input.Examples of user input include receiving a gesture on a touch-sensitivedisplay or mechanical user input device, such as a rotatable crown orbutton. Focus indicator 1320 may aid in a user concentrating on aparticular workout metric that is important to the user or for theparticular workout type.

As explained above, the workout metrics associated with a given workouttype may be configurable. FIG. 14 depicts interface 14 for the “Running”workout type but with a different set of workout metrics associated withthe “Running” workout type as compared to interface 1300 of FIG. 13.Interface 1400 includes first indicator 1410 for the distance workoutmetric, second indicator 1412 for the pace workout metric, thirdindicator 1414 for the Calories workout metric, fourth indicator 1416for the time elapsed workout metric, and fifth indicator 1418 for theheartrate workout metric. In interface 1400, focus indicator 1420 hasbeen moved to represent that second indicator 1412 represents thefocused workout metric. While two example interfaces having two and fiveworkout metric indicators have been provided, other numbers ofindicators may be included in the pro-view. For example, the pro-viewmay include exactly four indicators of workout metrics. Additionally,the different indicators for the workout metrics may use differentcolors to set apart the different indicators and make for a morepleasant viewing experience.

The ordering of the workout metric indicators in pro-view displays maybe configurable. For example, the position of first indicator 1410 withrespect to second indicator 1412 may be changed. In some cases, theposition may be changed by, for example, dragging the first indicator toa new position while in a position configuration user interface.

Also at block 904, before or after displaying the pro-view, the workoutmay also be initiated. Initiating the workout can include activating oneor more activity sensors (e.g., sensors 168, 359, and 520) and recordingactivity data provided by those one or more activity sensors. In someexamples, the activity sensors activated at block 904 can be selectedbased on the type of workout selected at block 902. For example, abiometric sensor for measuring heart rate, GPS sensor for measuringposition, and accelerometer for measuring motion to determine distancetraveled can be activated if a running type of workout was selected atblock 902. However, if a cycling type of workout was selected at block902, a biometric sensor for measuring heart rate and a GPS sensor formeasuring position may be activated at block 902, but an accelerometermay not be activated. This may be done because an accelerometer may notprovide reliable information in determining distance traveled on a bikeand can be left inactive to save power. Other combinations of activitysensors can selectively be activated for other types of workouts.

Referring back to FIG. 9, at block 906 one or more processors of thedevice can receive activity data that is representative of sensedphysical activity of a user from an activity sensor. At block 908, theone or more processors can process the received activity data to updatevalues of attributes of the workout stored on the device. For example, atimer can be used to update the duration of the workout based on adifference between a current value of the timer and a value of the timerwhen the workout was initiated at block 904. Additionally, anaccelerometer, motion sensor, gyroscope, biometric sensor, and/or GPSsensor can be used to update a distance traveled during the workout andcan additionally or alternatively be used to update a number of Caloriesburned during the workout (in combination with the user's age, gender,and weight). The timer can be used in combination with theaccelerometer, motion sensor, and/or GPS sensor to update a pace of theuser during the workout. Other activity sensors can similarly be used todetermine and update values of other workout attributes.

At block 910, one or more processors of the device can update thepro-view display (e.g., those shown in FIGS. 13 and 14) to reflect theupdated values of the workout metrics determined at block 908. Forexample, with reference to FIG. 14, the first indicator 1310 can beadjusted to reflect the total distance traveled, second indicator 1312can be moved to reflect the updated pace value, and third indicator 1314can be updated to reflect the updated value of Calories burned, fourthindicator 1416 can be updated to reflect the updated value of the timeelapsed, and fifth indicator 1418 can be update to reflect the updatedvalue of the heart rate.

Blocks 906, 908, and 910 can continue to be repeated to provide the userwith up to date information associated with the workout metrics of theworkout type via the pro-view display. In some examples where theworkout application is running in the background of the device or whilethe display of the device is deactivated, block 910 can be omitted andblocks 906 and 908 can repeatedly be performed to monitor the user'sworkout and update the monitored workout metrics such that an accuratedisplay of the metrics can later be provided to the user when thephysical activity application is reopened or the display of the deviceis activated. In some examples, upon activating the display of thedevice, the workout interface previously displayed (e.g., one of theinterfaces displayed in FIGS. 13 and 14) before deactivating the displaycan be displayed. This workout interface can be displayed while thedevice is in a locked state or can be displayed in response to unlockingthe device.

In block 912, one or more processors of the device can cause thepro-view display to continue to be displayed. Alternatively, somethingmay trigger a simple-view display to be displayed. For example, agesture, such as a horizontal swipe, may be detected that causes atransition from the pro-view display to the simple-view display. Otheruser input could also cause the transition from the pro-view display tothe simple-view display.

In block 914, the simply-view display is displayed on the display of thedevice. The simple-view display includes an indicator for less than allof the workout metrics associated with the selected workout type ofblock 902. For example, FIG. 15 depicts interface 1500, which is anexample of a simple view. Interface 1500 includes a focus indicator 1510for the workout metric that was focused in the pro-view display. In thecase of interface 1500, the pro-view display (i.e., interface 1400 ofFIG. 14) was focusing the pace workout metric. Accordingly, focusedworkout metric 1512 is the pace workout metric and focused indicator1510 represents a value of the pace. Interface 1500 does not include anindicator representative of the other workout metrics included in thepro-view display. For example, neither progress indicator 1506 nor goalindicator 1508 represent any of the workout metrics represented in thepro-view display. In other examples, however, progress indicator 1506and goal indicator 1508 may be related to one of the workout metrics ofthe pro-view display.

Referring back to FIG. 9, at block 916 one or more processors of thedevice can receive activity data that is representative of sensedphysical activity of a user from an activity sensor. At block 918, theone or more processors can process the received activity data to updatevalues of workout metrics of the workout stored on the device. Forexample, a timer can be used to update the duration of the workout basedon a difference between a current value of the timer and a value of thetimer when the workout was initiated at block 904. Additionally, anaccelerometer, motion sensor, gyroscope, biometric sensor, and/or GPSsensor can be used to update a distance traveled during the workout andcan additionally or alternatively be used to update a number of Caloriesburned during the workout (in combination with the user's age, gender,and weight). The timer can be used in combination with theaccelerometer, motion sensor, and/or GPS sensor to update a pace of theuser during the workout. Other activity sensors can similarly be used todetermine and update values of other workout attributes.

At block 920, one or more processors of the device can update thesimple-view display (e.g., those shown in FIGS. 15, 16, 19 and 20) toreflect the updated values of the workout metrics determined at block918. For example, with reference to FIG. 15, the focused indicator 1510can be adjusted to reflect an updated value for the pace.

Blocks 916, 918, and 920 can continue to be repeated to provide the userwith up to date information associated with the attributes of theworkout via the workout interface. In some examples where the workoutapplication is running in the background of the device or while thedisplay of the device is deactivated, block 920 can be omitted andblocks 916 and 918 can repeatedly be performed to monitor the user'sworkout and update the monitored attributes such that an accuratedisplay of the attributes can later be provided to the user when thephysical activity application is reopened or the display of the deviceis activated. In some examples, upon activating the display of thedevice, the workout interface previously displayed (e.g., one of theinterfaces displayed in FIGS. 15, 16, 19, and 20) before deactivatingthe display can be displayed. This workout interface can be displayedwhile the device is in a locked state or can be displayed in response tounlocking the device.

In block 922, one or more processors of the device can cause thesimple-view display to continue to be displayed. Alternatively,something may trigger the pro-view to be displayed. For example, agesture, such as a horizontal swipe, may be detected that causes atransition from the simple-view display to the pro-view display. Otheruser input could also cause the transition from the pro-view display tothe simple-view display.

In the case of the simple-view display in FIG. 15, a transition back tothe pro-view would cause the pro-view display of interface 1400 (FIG.14) to be displayed. The focus of the pace workout metric, as shown byfocused indicator 1510 and focused workout metric 1512, is carried overto the pro-view as indicated by focus indicator 1420 of interface 1400(FIG. 14).

When simple-view is displayed, focused workout metric 1512 and itsrepresentative focused indicator 1510 may be changed. For example, byreceiving a user input, such as a gesture on a touch-sensitive screen orother user input on a rotatable crown or button, focused workout metricmay be changed to the distance workout metric, which is depicted insimple-view display in interface 1600 of FIG. 16. In interface 1600,focused workout metric 1612 is the distance workout metric and focusedindicator 1610 represents a value for focused workout metric 1612.

If the focused workout metric of the simple-view display changes, as isthe case with the change from interface 1500 of FIG. 15 to interface1600 of FIG. 16, the focused indicator will change with a transitionback to the pro-view as described above with respect to block 922. Forexample, the result of a transition of the simple-view display ofinterface 1600 of FIG. 16 back to a pro-view display is represented ininterface 1700 of FIG. 17, which shows a pro-view display with focusindicator 1720 now highlighting first indicator 1710 representing thedistance workout metric.

The transition from the pro-view back to the simple view operates in asimilar manner. For example, if the focus indicator changes from thefirst indicator (e.g., first indicator 1710 in interface 1700 of FIG.17) to the fourth indicator (e.g., fourth indicator 1816 of interface1800 of FIG. 18), then the result of a transition from the pro-viewdisplay to the simple-view display is shown in the simple-view displayof interface 1900 of FIG. 19, which depicts focused workout metric 1912being the elapsed time workout metric that is represented by focusedindicator 1910.

The simple-view display of interface 2000 of FIG. 20 depicts anotherchange in the focused workout metric as compared to the simple-viewdisplay in interface 1700 of FIG. 17. Focus workout metric 2012 is nowthe Calories workout metric, which is represented by focused indicator2010. The result of a transition back to the pro-view display isdepicted by the pro-view display of interface 2100 of FIG. 21. Ininterface 2100, focus indicator 2120 is now on third indicator 2114,which represents the Calories workout metric.

The transitions between pro-views and simple-views may use animations.For example, the focused workout metric of the pro-view display may beanimated to move into position in the simple-view display. Similaranimations can also be used for the transitions between simple-views andpro-views.

User input, such as gestures, can also be used to transition to otherdisplays, such as a workout control or a music control. For example,FIG. 22 depicts interface 2200 for controlling workout 2202 havingcontrol buttons that include, stop button 2204 and pause button 2206.Activation of stop button 2204 ends the workout. Activation of pausebutton 2206, pauses the workout (for example, pauses the collection orrecording of activity data) and displays a paused workout control, asdepicted in interface 2300 of FIG. 23, which includes stop button 2204and resume button 2302 that resumes the workout. FIG. 24 depicts anexample music control in interface 2400 for controlling music 2400 withskip button 2404 for skipping the current music and pause button 2406for pausing the music.

While process 900 (FIG. 9) is illustrated as starting with the pro-view,other embodiments of process 900 may start with the simple-view. In somecases, the initial view that is displayed may be user configurable orbased on last view used during the last workout.

FIG. 25 shows a functional block diagram of an electronic device 25configured in accordance with the principles of the various describedexamples. The functional blocks of the device can be implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 25 can be combined or separated into sub-blocks to implement theprinciples of the various described examples. Therefore, the descriptionherein optionally supports any possible combination or separation orfurther definition of the functional blocks described herein.

As shown in FIG. 25, electronic device 2500 can include atouch-sensitive display unit 2504 configured to display graphicalobjects and receive user gestures, activity sensor units 2506 configuredto detect movement associated with the electronic device, and aprocessing unit 2502. In some examples, processing unit 2502 can includean identifying unit 2508, a movement detecting unit 2510, a generatingunit 2512, a determining unit 2514, a gesture detecting unit 2516, and adisplaying unit 2518.

Processing unit 2502 can be configured to detect (e.g., usingidentifying unit 2508) an identification of a type of workout to beperformed. The type of workout is associated with a plurality of workoutmetrics, including a first workout metric and a second workout metric.Movement detecting unit 2510 can be configured to detect movementassociated with an electronic device using activity sensor units 2506.Generation unit 2512 can be configured to generate activity data basedon the detected movement from movement detecting unit 2510. Determiningunit 2514 can be configured to determine a current value of the firstworkout metric and a current value of a second workout metric based onthe activity data. Gesture detecting unit 2516 can be configured todetect a first user gesture corresponding to a request to displayworkout metric data. Displaying unit 2518 can be configured to, inresponse to gesture detecting unit 2516, cause, on the touch-sensitivedisplay unit 2504 a first display. The first display can include aplurality of indicators representative of the plurality of workoutmetrics, including a first indicator representative of the first workoutmetric and a second indicator representative of the second workoutmetric. The first display also can include a focus indicator for one ofthe plurality of indicators, wherein the focus indicator indicates afocused workout metric. The gesture detecting unit 25 can be furtherconfigured to detect, while the first displaying is being displayed, asecond user gesture corresponding to a request to transition between thefirst display and a second display. Displaying unit 2518 can be furtherconfigured to, in response to the second user gesture being detectedwhile the first display is being displayed, cause, on thetouch-sensitive display unit a first transition to the second display.The second display can include an indicator representative of thefocused workout metric. Not all of the plurality of workout metrics isrepresented in the second display. Gesture detecting unit 2516 can befurther configured to, while the second display is being displayed,detect a third user gesture corresponding to a request to transitionbetween the second display and the first display. Displaying unit 2518can be further configured to, in response to the third user gesturebeing detected while the second display is being displayed, cause, onthe touch-sensitive display unit a second transition to the firstdisplay.

In some examples, the plurality workout metrics that are associated withthe type of workout are configurable.

In some examples, the plurality of workout metrics includes a thirdworkout metric and a fourth workout metric, and the plurality ofindicators representative of the plurality of workout metrics furtherincludes a third indicator representative of a third workout metricassociated with the type of workout and a fourth indicatorrepresentative of a fourth workout metric associated with the type ofworkout. The plurality of workout metrics include at least four workoutmetrics selected from: a workout metric related to calories, a workoutmetric related to heart rate, a workout metric related to speed, aworkout metric related to distance traveled, and a workout metricrelated to time. In some examples, the plurality of indicators in thefirst display includes only four indicators representative of workoutmetrics.

In some examples, the first indicator has a position relative to thesecond indicator in the first display. Gesture detecting unit 2516 canbe further configured to detect a fourth user gesture corresponding to arequest to change the position of the first indicator relative to thesecond indicator in the first display. Processing unit 2502 can befurther configured to have optional changing unit 2520, which can beconfigured to, in response to the fourth user gesture being detected,change the position of the first indicator relative to the secondindicator.

In some examples, the first indicator has a first color and the secondindicator has a second color different than the first color. In someexamples, the transition from the first display to the second displayincludes an animation. In some examples, gesture detecting unit 2516 canbe further configured to detect a fifth user gesture corresponding to arequest to transition from the first display or the second display to athird display. Displaying unit 2518 can be further configured to, inresponse to the fifth user gesture being detected while the firstdisplay or the second display is being displayed, cause on thetouch-sensitive display unit the third display, including workoutcontrols or music controls.

In some examples, gesture detecting unit 2516 can be configured to,while the first display is being displayed, detect a sixth user gesturecorresponding to a request to move the focus indicator to a differentindicator of the plurality of indicators on the first display.Displaying unit 2518 can be further configure to, in response to thesixth user gesture being detected, move the focus indicator to thedifferent indicator on the first display.

In some examples, generation unit 2512 can be further configured togenerate the activity data after gesture detecting unit 2516 detects thefirst user gesture corresponding to the request to display workoutmetrics.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

1. (canceled)
 2. An electronic device, comprising: a touch-sensitivedisplay; one or more processors; memory; and one or more programs storedin the memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions for:receiving a first user input to initiate a workout session; in responseto detecting the first user input, displaying, on the touch-sensitivedisplay, a first user interface of a workout application; whiledisplaying the first user interface, receiving a second user input; andin response to receiving the second user input: ceasing to display thefirst user interface of the workout application; and displaying, on thetouch-sensitive display, a second user interface of a music applicationdifferent from the workout application.
 3. The electronic device ofclaim 2, wherein the second user input includes a swipe gesture.
 4. Theelectronic device of claim 2, wherein the one or more programs furtherinclude instructions for: in response to receiving the second userinput: displaying an animation during a transition between the firstuser interface of the workout application and the second user interfaceof the music application.
 5. The electronic device of claim 2, whereinthe second user input includes a swipe gesture in a first direction, andwherein the one or more programs further include instructions for: whiledisplaying the second user interface of the music application, receivinga third user input, wherein the third user input includes a swipegesture in a second direction opposite the first direction; and inresponse to receiving the third user input: ceasing to display thesecond user interface of the music application; and displaying, on thetouch-sensitive display, the first user interface of the workoutapplication.
 6. The electronic device of claim 2, wherein the first userinterface of the workout application includes a plurality of indicatorsrepresentative of a plurality of workout metrics, wherein the pluralityof workout metrics includes calories, heart rate, speed, distancetraveled, elapsed time, or any combination thereof.
 7. The electronicdevice of claim 6, wherein the plurality of workout metrics is userconfigurable via a user configuration interface.
 8. The electronicdevice of claim 6, wherein the one or more programs further includeinstructions for: receiving activity data corresponding to detectedmovement of the electronic device; and updating at least one of theplurality of indicators representative of the plurality of workoutmetrics based on the activity data.
 9. The electronic device of claim 2,wherein the second user interface of the music application includes aplurality of music control affordances, wherein each music controlaffordance, when selected via user input, is configured to control audiooutput via the electronic device.
 10. The electronic device of claim 9,wherein the plurality of music control affordances includes a skipaffordance or a pause affordance.
 11. The electronic device of claim 2,wherein the second user interface of the music application includes anaudio indicator corresponding to a current audio file configured to beoutput via the electronic device.
 12. A non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a touch-sensitivedisplay, the one or more programs including instructions for: receivinga first user input to initiate a workout session; in response todetecting the first user input, displaying, on the touch-sensitivedisplay, a first user interface of a workout application; whiledisplaying the first user interface, receiving a second user input; andin response to receiving the second user input: ceasing to display thefirst user interface of the workout application; and displaying, on thetouch-sensitive display, a second user interface of a music applicationdifferent from the workout application.
 13. A method, comprising: at anelectronic device including a touch-sensitive display: receiving a firstuser input to initiate a workout session; in response to detecting thefirst user input, displaying, on the touch-sensitive display, a firstuser interface of a workout application; while displaying the first userinterface, receiving a second user input; and in response to receivingthe second user input: ceasing to display the first user interface ofthe workout application; and displaying, on the touch-sensitive display,a second user interface of a music application different from theworkout application.